Task: Perform Release Testing
The purpose of this task is to test the Release Package before moving it to the production environment. Different types of testing, as agreed in the test strategy, are performed. These would typically include release testing, test of back out procedures, etc.
Relationships
RolesPrimary: Additional: Assisting:
Outputs
Main Description
The release testing is performed in a separate dedicated test environment with production like data setup, i.e. it is representative of the production environment to the extent possible. This test environment must be created considering all the requirements mentioned in the Release And Deployment Plan. The Operation Acceptance Testing (OAT) is carried out as a part of release testing, main purpose of which is to test and confirm the extent of a negative impact in the production environment on implementing a new Release Package. A release test must check whether the service components are integrated correctly, and the release can be installed, built and tested in the target environment.

This environment should be change controlled to ensure the integrity of the release is maintained and any required refreshes are completed to ensure it matches the current live baseline.

Following any changes made as a result of UAT, this will provide a final rehearsal and test of the documented implementation steps increasing familiarity for the engineers involved and ensuring timings set are realistic. This ensures that if executed as planned, the end result is a fully installed release.

Additionally, testing should also be done to check for deployment execution errors. In case any defects are found, the scripts may have to be updated and this step may need to be carried out again.

Test execution must happen as planned in line with the Client acceptance criteria.

All test defects must be logged, monitored and tracked to closure before getting into the next phase of testing. Release Test Results must be documented and communicated to all relevant stakeholders.